Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 197b54f984f3763d9368b65cb81095edb1136329c3410571faf7a9631b76ffd4

Tx prefix hash: 317559c9d53cbb6e5d754fe9bd45488dd4964a0663ad58ae27e98da3c6e2cc81
Tx public key: d6413eb44bdc6fa2e7a9ad8050dbcaae18a2210b0654ea93f2ef3f4cd62ac0e6
Timestamp: 1711786053 Timestamp [UCT]: 2024-03-30 08:07:33 Age [y:d:h:m:s]: 01:019:02:03:39
Block: 989486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274586 RingCT/type: yes/0
Extra: 01d6413eb44bdc6fa2e7a9ad8050dbcaae18a2210b0654ea93f2ef3f4cd62ac0e602110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c161a487af0802235d99d644b6b20fb29ce3ef30ad815439efc7b3deba52810 0.600000000000 1449783 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": 989496, "vin": [ { "gen": { "height": 989486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c161a487af0802235d99d644b6b20fb29ce3ef30ad815439efc7b3deba52810" } } ], "extra": [ 1, 214, 65, 62, 180, 75, 220, 111, 162, 231, 169, 173, 128, 80, 219, 202, 174, 24, 162, 33, 11, 6, 84, 234, 147, 242, 239, 63, 76, 214, 42, 192, 230, 2, 17, 0, 0, 0, 12, 0, 17, 5, 91, 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