Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ef96c3683eaaf711bc559cde9dc913772175860861461c1aaab1503582d33c5

Tx prefix hash: af4b363539e837eadf2c7d2e1b0f9962055a4ff3d89e351c58b56dd3fd81b3eb
Tx public key: 54e94269a62db753f67a9471361fb763aa1f75142810bc5d9edee3381301fc73
Timestamp: 1727449067 Timestamp [UCT]: 2024-09-27 14:57:47 Age [y:d:h:m:s]: 00:057:17:13:25
Block: 1119316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41242 RingCT/type: yes/0
Extra: 0154e94269a62db753f67a9471361fb763aa1f75142810bc5d9edee3381301fc73021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5f3b21718dc4e2387ea7d59abcf681f294b4f5d0d91517b1f65113e1f879680 0.600000000000 1600831 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": 1119326, "vin": [ { "gen": { "height": 1119316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5f3b21718dc4e2387ea7d59abcf681f294b4f5d0d91517b1f65113e1f879680" } } ], "extra": [ 1, 84, 233, 66, 105, 166, 45, 183, 83, 246, 122, 148, 113, 54, 31, 183, 99, 170, 31, 117, 20, 40, 16, 188, 93, 158, 222, 227, 56, 19, 1, 252, 115, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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