Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fb7799549050271dd390059778ebf84843ed1044ca477b9e6ca0918593aa2cc

Tx prefix hash: 608d69e833332e8a6722096c953f6f79eefdd821c8ef241e0effcbde79aef677
Tx public key: ae80d3bda58e1d3f3f958d7a5aa15eb7df9936fcabd30c99bb19b3d4526c6d0c
Timestamp: 1761723108 Timestamp [UCT]: 2025-10-29 07:31:48 Age [y:d:h:m:s]: 00:007:18:18:14
Block: 1400351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5530 RingCT/type: yes/0
Extra: 01ae80d3bda58e1d3f3f958d7a5aa15eb7df9936fcabd30c99bb19b3d4526c6d0c02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 656547476c404975f475d501bdbcb04a7702f802012fff7696ec609aa83f7dd8 0.600000000000 1888658 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": 1400361, "vin": [ { "gen": { "height": 1400351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "656547476c404975f475d501bdbcb04a7702f802012fff7696ec609aa83f7dd8" } } ], "extra": [ 1, 174, 128, 211, 189, 165, 142, 29, 63, 63, 149, 141, 122, 90, 161, 94, 183, 223, 153, 54, 252, 171, 211, 12, 153, 187, 25, 179, 212, 82, 108, 109, 12, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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