Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fd95642334922f0aff6042c5d5d12037b3ded430b24df44196ab2a3b5df49cf

Tx prefix hash: ea36a1136b40c7c134190a954baf798d2f4eae5dd84702da9d994ad21b5f31c9
Tx public key: 1f3d79c0bb1114abf0cb07580c49ed2635f5f036e4b3fe2039ef5d96cba55787
Timestamp: 1745384424 Timestamp [UCT]: 2025-04-23 05:00:24 Age [y:d:h:m:s]: 00:260:13:54:18
Block: 1267490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184029 RingCT/type: yes/0
Extra: 011f3d79c0bb1114abf0cb07580c49ed2635f5f036e4b3fe2039ef5d96cba5578702110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c33eb3975ed4c41f032e89cffb399679a605d08732f93263ad436b9df7cf0306 0.600000000000 1754719 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": 1267500, "vin": [ { "gen": { "height": 1267490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c33eb3975ed4c41f032e89cffb399679a605d08732f93263ad436b9df7cf0306" } } ], "extra": [ 1, 31, 61, 121, 192, 187, 17, 20, 171, 240, 203, 7, 88, 12, 73, 237, 38, 53, 245, 240, 54, 228, 179, 254, 32, 57, 239, 93, 150, 203, 165, 87, 135, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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