Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c55a591eef6879033e40a07ac7ed2eec53addeeec9bc6522f2bc36cd686a8686

Tx prefix hash: 6707acc4d35018d358876f7d58db4d23e6bd09b9b3b171f28924ad231a08ac03
Tx public key: 4f8c40d29e69f7dc30978c8fa2915477fa6c8de217e814ce20c8a3bf9a1178c3
Timestamp: 1759185590 Timestamp [UCT]: 2025-09-29 22:39:50 Age [y:d:h:m:s]: 00:008:13:13:19
Block: 1379297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6125 RingCT/type: yes/0
Extra: 014f8c40d29e69f7dc30978c8fa2915477fa6c8de217e814ce20c8a3bf9a1178c3021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccf4dd91ad1105e1c1db119fe116e4bd67cd5f1b559e0d808bfee52c3d49bf0b 0.600000000000 1867394 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": 1379307, "vin": [ { "gen": { "height": 1379297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccf4dd91ad1105e1c1db119fe116e4bd67cd5f1b559e0d808bfee52c3d49bf0b" } } ], "extra": [ 1, 79, 140, 64, 210, 158, 105, 247, 220, 48, 151, 140, 143, 162, 145, 84, 119, 250, 108, 141, 226, 23, 232, 20, 206, 32, 200, 163, 191, 154, 17, 120, 195, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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