Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36cf650d8be06c1f84117714c15e9b3f38d363771d13b3acc1de3faf9ff6c774

Tx prefix hash: 6e3ef59c5d49de95abff87ae040cd0605241fadec7f0b61ce8eb7859dc31097e
Tx public key: 88c8cf4b8abeb89c178fd7b5c0e0429d8d865229db4bc8daa773e2a6c95527be
Timestamp: 1718363628 Timestamp [UCT]: 2024-06-14 11:13:48 Age [y:d:h:m:s]: 00:290:08:38:28
Block: 1043993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207488 RingCT/type: yes/0
Extra: 0188c8cf4b8abeb89c178fd7b5c0e0429d8d865229db4bc8daa773e2a6c95527be02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53f2f53537440975e8d90508f38e359f47bb30caa101ad515b50c9864e5108c1 0.600000000000 1513178 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": 1044003, "vin": [ { "gen": { "height": 1043993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53f2f53537440975e8d90508f38e359f47bb30caa101ad515b50c9864e5108c1" } } ], "extra": [ 1, 136, 200, 207, 75, 138, 190, 184, 156, 23, 143, 215, 181, 192, 224, 66, 157, 141, 134, 82, 41, 219, 75, 200, 218, 167, 115, 226, 166, 201, 85, 39, 190, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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