Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afc98cf0e520027cef2fe68d61ddaa0d2bf0b64e51e2cc8a5c47d3dd4776bf46

Tx prefix hash: d0ba69b094ccc837f214835342cca66cdd3ced0d9fa2c64d54da6edacc85def6
Tx public key: 8f6bec6a2554752c73a3986c74fc282c046eb3b85edd47e16ca42a12a9fa118d
Timestamp: 1727999841 Timestamp [UCT]: 2024-10-03 23:57:21 Age [y:d:h:m:s]: 00:177:06:02:14
Block: 1123884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126466 RingCT/type: yes/0
Extra: 018f6bec6a2554752c73a3986c74fc282c046eb3b85edd47e16ca42a12a9fa118d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68696a3add3c485719a2d4c3d8f36e13204e1d0e913a31a4a6cae929e6c07def 0.600000000000 1606429 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": 1123894, "vin": [ { "gen": { "height": 1123884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68696a3add3c485719a2d4c3d8f36e13204e1d0e913a31a4a6cae929e6c07def" } } ], "extra": [ 1, 143, 107, 236, 106, 37, 84, 117, 44, 115, 163, 152, 108, 116, 252, 40, 44, 4, 110, 179, 184, 94, 221, 71, 225, 108, 164, 42, 18, 169, 250, 17, 141, 2, 17, 0, 0, 0, 3, 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