Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec46f8c4916e5f7e55155791e0aff0d0affb3c6c47bbc75a95ca1b5691de5ad4

Tx prefix hash: a0c9948f6e4c31489923843857710f85c4cdbb9ff83b29c72b21061a4613e0f9
Tx public key: 00580cf2279aa8416f02c9a87b2fe204f36657df3bc245737b4471ef8e4d5a89
Timestamp: 1715202358 Timestamp [UCT]: 2024-05-08 21:05:58 Age [y:d:h:m:s]: 01:182:03:51:21
Block: 1017788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388789 RingCT/type: yes/0
Extra: 0100580cf2279aa8416f02c9a87b2fe204f36657df3bc245737b4471ef8e4d5a890211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 114a306adca00f3001f7524053667cfdc158b953301b5a0d0c1afb2cbc3df242 0.600000000000 1481573 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": 1017798, "vin": [ { "gen": { "height": 1017788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "114a306adca00f3001f7524053667cfdc158b953301b5a0d0c1afb2cbc3df242" } } ], "extra": [ 1, 0, 88, 12, 242, 39, 154, 168, 65, 111, 2, 201, 168, 123, 47, 226, 4, 243, 102, 87, 223, 59, 194, 69, 115, 123, 68, 113, 239, 142, 77, 90, 137, 2, 17, 0, 0, 0, 1, 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