Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ab1968e601c833d0ece0a293976c7c7479b8d52c0410ffdd487900cb4e75f8e

Tx prefix hash: aba32329eaccf4e55f1a79e2c9ae877316be6d46e1f37f5033c28b370fb6a1cc
Tx public key: e874c6de0846b21a75d1b66bbfa18731c679799e4f0837990a7fdfccc07714a0
Timestamp: 1734897460 Timestamp [UCT]: 2024-12-22 19:57:40 Age [y:d:h:m:s]: 00:081:11:19:35
Block: 1180973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57987 RingCT/type: yes/0
Extra: 01e874c6de0846b21a75d1b66bbfa18731c679799e4f0837990a7fdfccc07714a0021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cf09019671c07b0cd75e4cb836baee3c1a51fd0fef12ee37618415ebba49d2e 0.600000000000 1667388 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": 1180983, "vin": [ { "gen": { "height": 1180973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cf09019671c07b0cd75e4cb836baee3c1a51fd0fef12ee37618415ebba49d2e" } } ], "extra": [ 1, 232, 116, 198, 222, 8, 70, 178, 26, 117, 209, 182, 107, 191, 161, 135, 49, 198, 121, 121, 158, 79, 8, 55, 153, 10, 127, 223, 204, 192, 119, 20, 160, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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