Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b268e73a07ac2c0401716a7a2da3e4a8e481f7e237b0dae4ce3f682548d3f3c8

Tx prefix hash: f56424ec8b1b194830aaab87b4189720c67528a3a3a1ff835248140d0e385552
Tx public key: dd0051bfdba797da7fca184baf6233932621040b1dee405fc97e4fd5c44d0f20
Timestamp: 1753266002 Timestamp [UCT]: 2025-07-23 10:20:02 Age [y:d:h:m:s]: 00:074:14:27:17
Block: 1331585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52071 RingCT/type: yes/0
Extra: 01dd0051bfdba797da7fca184baf6233932621040b1dee405fc97e4fd5c44d0f2002110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9495b6d092a47de9b280be12d49df9e0ffda32d8e9b78144f16c5314eab2a0f 0.600000000000 1819380 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": 1331595, "vin": [ { "gen": { "height": 1331585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9495b6d092a47de9b280be12d49df9e0ffda32d8e9b78144f16c5314eab2a0f" } } ], "extra": [ 1, 221, 0, 81, 191, 219, 167, 151, 218, 127, 202, 24, 75, 175, 98, 51, 147, 38, 33, 4, 11, 29, 238, 64, 95, 201, 126, 79, 213, 196, 77, 15, 32, 2, 17, 0, 0, 0, 3, 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