Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f47b6b8090fbdd0ee0957d663573c6c77d83789d56b9464b0b881b77d6305b8d

Tx prefix hash: b964ea7ecbb0945eb6c3c91b62e89ec6a53440dce6d81f49acf81aef730b9156
Tx public key: 8c81ae242454f49b8d1aedada1f0768e25299bbd23f47712142787b2789f9822
Timestamp: 1750549504 Timestamp [UCT]: 2025-06-21 23:45:04 Age [y:d:h:m:s]: 00:151:22:05:14
Block: 1310074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106438 RingCT/type: yes/0
Extra: 018c81ae242454f49b8d1aedada1f0768e25299bbd23f47712142787b2789f9822021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad1440e9ba7990f0bd1049fccc1535c9eef48ae3eb818606d82b1998df6f8d85 0.600000000000 1797691 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": 1310084, "vin": [ { "gen": { "height": 1310074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad1440e9ba7990f0bd1049fccc1535c9eef48ae3eb818606d82b1998df6f8d85" } } ], "extra": [ 1, 140, 129, 174, 36, 36, 84, 244, 155, 141, 26, 237, 173, 161, 240, 118, 142, 37, 41, 155, 189, 35, 244, 119, 18, 20, 39, 135, 178, 120, 159, 152, 34, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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