Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfd0725358545c9a594bd928125cc47bfb5d3d933c846c97a2a1873b99156a72

Tx prefix hash: dc3e92fcb331488b67fbf71a1acd6a0d95ee2fd16d17b84d1a319750c01d0cd6
Tx public key: 858ec676e3160f14371d313f3b29df7777e273708854474ab2aa1fb74910dd05
Timestamp: 1713397177 Timestamp [UCT]: 2024-04-17 23:39:37 Age [y:d:h:m:s]: 01:016:06:12:38
Block: 1002797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272581 RingCT/type: yes/0
Extra: 01858ec676e3160f14371d313f3b29df7777e273708854474ab2aa1fb74910dd050211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a0b8b95cd07948d67a122fd8ea4de2391f33c00cf67cfa302eb55878761b5f3 0.600000000000 1463321 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": 1002807, "vin": [ { "gen": { "height": 1002797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a0b8b95cd07948d67a122fd8ea4de2391f33c00cf67cfa302eb55878761b5f3" } } ], "extra": [ 1, 133, 142, 198, 118, 227, 22, 15, 20, 55, 29, 49, 63, 59, 41, 223, 119, 119, 226, 115, 112, 136, 84, 71, 74, 178, 170, 31, 183, 73, 16, 221, 5, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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