Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc9736c351572ea1b6316111bd000a4bea1db832d7002ce284d06c2ede10ad50

Tx prefix hash: 6e4a5398c940895e6ad44cbdf2206b0adc8edb21011d137d1cfae0f6ed3d50d3
Tx public key: fd639de39d39202e82212c4a5e5d26437df90670e734270d7830371adb8c6a2f
Timestamp: 1720892081 Timestamp [UCT]: 2024-07-13 17:34:41 Age [y:d:h:m:s]: 00:337:23:58:29
Block: 1064967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241425 RingCT/type: yes/0
Extra: 01fd639de39d39202e82212c4a5e5d26437df90670e734270d7830371adb8c6a2f02110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19362b0c419cdd4c16c4d2201afb2bff625247102f30ca7450e1465c276ac2af 0.600000000000 1535508 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": 1064977, "vin": [ { "gen": { "height": 1064967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19362b0c419cdd4c16c4d2201afb2bff625247102f30ca7450e1465c276ac2af" } } ], "extra": [ 1, 253, 99, 157, 227, 157, 57, 32, 46, 130, 33, 44, 74, 94, 93, 38, 67, 125, 249, 6, 112, 231, 52, 39, 13, 120, 48, 55, 26, 219, 140, 106, 47, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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