Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 556aea8169158ff5246b338936ab8a48e2b7b68120c17421f52ca58aff82bf75

Tx prefix hash: fca142a6fb3e07978d4035a803a2f47cb942ea6ee6b54d3a0b3d390a43bf8ec2
Tx public key: dbd1c7cbd5f81cace4e97682197c2352488e1eaf4ed2bb8371e3bb92202f6419
Timestamp: 1744183828 Timestamp [UCT]: 2025-04-09 07:30:28 Age [y:d:h:m:s]: 00:273:06:09:42
Block: 1257553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193096 RingCT/type: yes/0
Extra: 01dbd1c7cbd5f81cace4e97682197c2352488e1eaf4ed2bb8371e3bb92202f64190211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 296fcad18748e324956df9d917c1f5f72af9895fc22b17b6b8b926cd81618b80 0.600000000000 1744680 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": 1257563, "vin": [ { "gen": { "height": 1257553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "296fcad18748e324956df9d917c1f5f72af9895fc22b17b6b8b926cd81618b80" } } ], "extra": [ 1, 219, 209, 199, 203, 213, 248, 28, 172, 228, 233, 118, 130, 25, 124, 35, 82, 72, 142, 30, 175, 78, 210, 187, 131, 113, 227, 187, 146, 32, 47, 100, 25, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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