Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcabb41bad270b7e239fab26af9a9ac4fbdf43899fcf8c5fe3c8756689666917

Tx prefix hash: 530ea89f1e26bbb5e1346f2651cb446e685f6eca5f49fa11f1fd18182c074fcb
Tx public key: 6de855f1b54bdb6a937fed73357cfa4c119c4f5c0370fce814b6a2e4de27df91
Timestamp: 1756012883 Timestamp [UCT]: 2025-08-24 05:21:23 Age [y:d:h:m:s]: 00:094:08:57:15
Block: 1353194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67394 RingCT/type: yes/0
Extra: 016de855f1b54bdb6a937fed73357cfa4c119c4f5c0370fce814b6a2e4de27df910211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0db72d5fe488e13943c7322e5a7c2e54ed44caa168879fef816f598ed34a86f 0.600000000000 1841167 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": 1353204, "vin": [ { "gen": { "height": 1353194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0db72d5fe488e13943c7322e5a7c2e54ed44caa168879fef816f598ed34a86f" } } ], "extra": [ 1, 109, 232, 85, 241, 181, 75, 219, 106, 147, 127, 237, 115, 53, 124, 250, 76, 17, 156, 79, 92, 3, 112, 252, 232, 20, 182, 162, 228, 222, 39, 223, 145, 2, 17, 0, 0, 0, 3, 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