Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 178f3ab0bfc1f81edae6f94c7861383039712439ff92063341980a132af1efa2

Tx prefix hash: 9f9b65b4d5444f2e683933e9ad7fcb7799cd57718081dc98186b8d82c06df0d8
Tx public key: b3d384a9790beddee49e2c63dd8e0d130dcb37b09f05846e8b4c167196f1bb64
Timestamp: 1713475217 Timestamp [UCT]: 2024-04-18 21:20:17 Age [y:d:h:m:s]: 00:226:13:11:11
Block: 1003457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162194 RingCT/type: yes/0
Extra: 01b3d384a9790beddee49e2c63dd8e0d130dcb37b09f05846e8b4c167196f1bb64021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43441586d5347e250b55f6d410ba6d7177f32bbc7faeafac70dfd4460c16b472 0.600000000000 1463997 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": 1003467, "vin": [ { "gen": { "height": 1003457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43441586d5347e250b55f6d410ba6d7177f32bbc7faeafac70dfd4460c16b472" } } ], "extra": [ 1, 179, 211, 132, 169, 121, 11, 237, 222, 228, 158, 44, 99, 221, 142, 13, 19, 13, 203, 55, 176, 159, 5, 132, 110, 139, 76, 22, 113, 150, 241, 187, 100, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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