Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 909cb573cdd12b88ce39c310457592d3334b212fd6a47286aef3e6d4c77009e0

Tx prefix hash: 90e92d312f655de2031ebded1e0fc4208bba3b18b073c1ad8c8b518cb26e9a6a
Tx public key: 1bdf1d33a5601346637fcfb8d6c05139aeef78764e8a8d21378be84a213cd1a3
Timestamp: 1753029810 Timestamp [UCT]: 2025-07-20 16:43:30 Age [y:d:h:m:s]: 00:114:05:22:34
Block: 1329646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80437 RingCT/type: yes/0
Extra: 011bdf1d33a5601346637fcfb8d6c05139aeef78764e8a8d21378be84a213cd1a302110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af95bde8e1753d51d6bf48f355b5ff18bc4f8a5f317f362b85b6377ce7720228 0.600000000000 1817435 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": 1329656, "vin": [ { "gen": { "height": 1329646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af95bde8e1753d51d6bf48f355b5ff18bc4f8a5f317f362b85b6377ce7720228" } } ], "extra": [ 1, 27, 223, 29, 51, 165, 96, 19, 70, 99, 127, 207, 184, 214, 192, 81, 57, 174, 239, 120, 118, 78, 138, 141, 33, 55, 139, 232, 74, 33, 60, 209, 163, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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