Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1e4f62cf191836f941a95545f250a83e32220aa595d8d35a54def3703221a92

Tx prefix hash: 6fceb00fb8a2459ebefde1bf6453e2ce1d54592d0278ff0198992f407a7f60f4
Tx public key: 2f24c7fc26ee4e39928f2649c366784396c26bbf8bc8f247a4c0ef4d1a8311f1
Timestamp: 1725290581 Timestamp [UCT]: 2024-09-02 15:23:01 Age [y:d:h:m:s]: 01:065:20:23:01
Block: 1101416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305501 RingCT/type: yes/0
Extra: 012f24c7fc26ee4e39928f2649c366784396c26bbf8bc8f247a4c0ef4d1a8311f1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b70d1fcd5972ffcb91ef2a24834a5b9b7bb72152f1a0695bebac4d21299f76bc 0.600000000000 1577457 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": 1101426, "vin": [ { "gen": { "height": 1101416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b70d1fcd5972ffcb91ef2a24834a5b9b7bb72152f1a0695bebac4d21299f76bc" } } ], "extra": [ 1, 47, 36, 199, 252, 38, 238, 78, 57, 146, 143, 38, 73, 195, 102, 120, 67, 150, 194, 107, 191, 139, 200, 242, 71, 164, 192, 239, 77, 26, 131, 17, 241, 2, 17, 0, 0, 0, 5, 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