Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d82c4e92ac08772b8e13bd3d71740182cbfd36638214c23316aad9a00d8a734

Tx prefix hash: 489a99dc4823c7d079db150530dbeae726f8505db08fa2cf812af0b15c2729ef
Tx public key: 0faa79716c23b1527cd4566e6d15b2032845d6a12d58dff8f8c9de3cc46ae83c
Timestamp: 1708243610 Timestamp [UCT]: 2024-02-18 08:06:50 Age [y:d:h:m:s]: 01:040:00:05:49
Block: 960087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289615 RingCT/type: yes/0
Extra: 010faa79716c23b1527cd4566e6d15b2032845d6a12d58dff8f8c9de3cc46ae83c021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c38f861c86ae22344795216b5a967e600ca87848250654361d9e4a3dcfcb5a3 0.600000000000 1419646 of 15

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": 960097, "vin": [ { "gen": { "height": 960087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c38f861c86ae22344795216b5a967e600ca87848250654361d9e4a3dcfcb5a3" } } ], "extra": [ 1, 15, 170, 121, 113, 108, 35, 177, 82, 124, 212, 86, 110, 109, 21, 178, 3, 40, 69, 214, 161, 45, 88, 223, 248, 248, 201, 222, 60, 196, 106, 232, 60, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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