Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a467e27a54c45e4be5c054333ac3d81bab09da8f09c5744ef0b81761463a5451

Tx prefix hash: 211df20ada5fe4e603f7c49c05957c8d6c2efd00f2cd0ce737890ced0029df9e
Tx public key: 7b4c70585bd8a9191028d5d24239db5c4d88e974abde5ff7cde422fec66a6ad5
Timestamp: 1728894751 Timestamp [UCT]: 2024-10-14 08:32:31 Age [y:d:h:m:s]: 00:244:16:56:07
Block: 1131303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174613 RingCT/type: yes/0
Extra: 017b4c70585bd8a9191028d5d24239db5c4d88e974abde5ff7cde422fec66a6ad50211000000023cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d675dd42644cbf44e88bf81c12b0f47eb7450ceb38048851caca4f8f0603dc3b 0.600000000000 1614192 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": 1131313, "vin": [ { "gen": { "height": 1131303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d675dd42644cbf44e88bf81c12b0f47eb7450ceb38048851caca4f8f0603dc3b" } } ], "extra": [ 1, 123, 76, 112, 88, 91, 216, 169, 25, 16, 40, 213, 210, 66, 57, 219, 92, 77, 136, 233, 116, 171, 222, 95, 247, 205, 228, 34, 254, 198, 106, 106, 213, 2, 17, 0, 0, 0, 2, 60, 208, 252, 6, 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