Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 88de1a65b4498a1db42df7bd1eb055a4cb883b4d40805334e1db8066a45d8219

Tx prefix hash: 6674f6d1b0e4726e54856a1af9ca1c0524c2b87b9060963a8e683acf9be471bc
Tx public key: 5e5d50ef7b665d6f4b91d0485481adddf89d89cb572dabac3d56f10400574663
Timestamp: 1634783521 Timestamp [UCT]: 2021-10-21 02:32:01 Age [y:d:h:m:s]: 03:019:00:40:18
Block: 357158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 791801 RingCT/type: yes/0
Extra: 015e5d50ef7b665d6f4b91d0485481adddf89d89cb572dabac3d56f104005746630211000000023fc41461000000000000000000

1 output(s) for total of 40.233489006000 dcy

stealth address amount amount idx
00: dc23d5219cf427990fffd4e97b4af0e943e2a35a4573dafd692723d45b8f4be7 40.233489006000 728392 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 357168, "vin": [ { "gen": { "height": 357158 } } ], "vout": [ { "amount": 40233489006, "target": { "key": "dc23d5219cf427990fffd4e97b4af0e943e2a35a4573dafd692723d45b8f4be7" } } ], "extra": [ 1, 94, 93, 80, 239, 123, 102, 93, 111, 75, 145, 208, 72, 84, 129, 173, 221, 248, 157, 137, 203, 87, 45, 171, 172, 61, 86, 241, 4, 0, 87, 70, 99, 2, 17, 0, 0, 0, 2, 63, 196, 20, 97, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8