Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b72cfb5ff8b805c80d9e368657cb95acd2af7c1db067a1108ce5483a99070612

Tx prefix hash: 485235843c9c565a5f95edd2661f69ba521016fa5ac1a6db05d223889ffe0fc8
Tx public key: 79c0a4ae5e4b5fe2268db82967e82c9530978246de9aee2c42eac464b3f1778e
Timestamp: 1747723996 Timestamp [UCT]: 2025-05-20 06:53:16 Age [y:d:h:m:s]: 00:182:07:46:29
Block: 1286867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128004 RingCT/type: yes/0
Extra: 0179c0a4ae5e4b5fe2268db82967e82c9530978246de9aee2c42eac464b3f1778e02110000000f9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d4d8d2c576292664ef650996d1f153df08f1d380ab35a72669b0a7b3ad3d535 0.600000000000 1774334 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": 1286877, "vin": [ { "gen": { "height": 1286867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d4d8d2c576292664ef650996d1f153df08f1d380ab35a72669b0a7b3ad3d535" } } ], "extra": [ 1, 121, 192, 164, 174, 94, 75, 95, 226, 38, 141, 184, 41, 103, 232, 44, 149, 48, 151, 130, 70, 222, 154, 238, 44, 66, 234, 196, 100, 179, 241, 119, 142, 2, 17, 0, 0, 0, 15, 159, 159, 230, 140, 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