Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 518b4dcedb52f29e0efca6ad4526e06f667df4bb00eed528a984035ad0d3e536

Tx prefix hash: bfc5253ecdbc8cd1b7732902f64c1bcb74716c1a1a665f130ec262110bc20682
Tx public key: 3383dd68b903f2c2f11a4e6c133df7072656cf89e4ad5a7d0cffac3fe38b5e24
Timestamp: 1714166219 Timestamp [UCT]: 2024-04-26 21:16:59 Age [y:d:h:m:s]: 00:323:16:17:34
Block: 1009182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231411 RingCT/type: yes/0
Extra: 013383dd68b903f2c2f11a4e6c133df7072656cf89e4ad5a7d0cffac3fe38b5e2402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f1fd12fc2ff22f10223a7c2258d85738bd9ad407ad1b912858ea8fe18479f4d 0.600000000000 1470782 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": 1009192, "vin": [ { "gen": { "height": 1009182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f1fd12fc2ff22f10223a7c2258d85738bd9ad407ad1b912858ea8fe18479f4d" } } ], "extra": [ 1, 51, 131, 221, 104, 185, 3, 242, 194, 241, 26, 78, 108, 19, 61, 247, 7, 38, 86, 207, 137, 228, 173, 90, 125, 12, 255, 172, 63, 227, 139, 94, 36, 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