Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3530d75d69f435da0e05b5695294c71a36d43e9346f601174fac047674a3588

Tx prefix hash: e3663acbb5a4f1aba0b0ad11281a3aa55cf91383106cc8e8dcf88c962ca07c05
Tx public key: fb720b8b549431bdd01877f19c124c4a5fef7ec0a4d201df211b52ce693a0cee
Timestamp: 1631716397 Timestamp [UCT]: 2021-09-15 14:33:17 Age [y:d:h:m:s]: 04:093:13:08:11
Block: 334359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100940 RingCT/type: yes/0
Extra: 01fb720b8b549431bdd01877f19c124c4a5fef7ec0a4d201df211b52ce693a0cee021100000018fdc024ec000000000000000000

1 output(s) for total of 47.889298722000 dcy

stealth address amount amount idx
00: d04d6f7efc301ae096ee9048d119340e91f80f2a7f0c91984ebdd9c995715ead 47.889298722000 689686 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": 334369, "vin": [ { "gen": { "height": 334359 } } ], "vout": [ { "amount": 47889298722, "target": { "key": "d04d6f7efc301ae096ee9048d119340e91f80f2a7f0c91984ebdd9c995715ead" } } ], "extra": [ 1, 251, 114, 11, 139, 84, 148, 49, 189, 208, 24, 119, 241, 156, 18, 76, 74, 95, 239, 126, 192, 164, 210, 1, 223, 33, 27, 82, 206, 105, 58, 12, 238, 2, 17, 0, 0, 0, 24, 253, 192, 36, 236, 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