Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d7610b40b9afbbad0202a8eb8543491302b05ec9887e165cee6de09d5707445

Tx prefix hash: 22007b730e49cec884300a207f542dcddf3f8b273827f35f24dae66b9395758a
Tx public key: 69ab3538207d5cd45720fad9a9e824ef62c55e227cfd9a2c9b9232e08dcd6e9d
Timestamp: 1710846824 Timestamp [UCT]: 2024-03-19 11:13:44 Age [y:d:h:m:s]: 01:014:21:08:47
Block: 981692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271590 RingCT/type: yes/0
Extra: 0169ab3538207d5cd45720fad9a9e824ef62c55e227cfd9a2c9b9232e08dcd6e9d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dee2e04c21f8a1050bec0fdc504e017e10c633f0f5504da4ffe89bafad1305a5 0.600000000000 1441789 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": 981702, "vin": [ { "gen": { "height": 981692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dee2e04c21f8a1050bec0fdc504e017e10c633f0f5504da4ffe89bafad1305a5" } } ], "extra": [ 1, 105, 171, 53, 56, 32, 125, 92, 212, 87, 32, 250, 217, 169, 232, 36, 239, 98, 197, 94, 34, 124, 253, 154, 44, 155, 146, 50, 224, 141, 205, 110, 157, 2, 17, 0, 0, 0, 2, 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