Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 313910900391f20e7996483dacd0761e916b68674cc93d803643b5942da3c4cf

Tx prefix hash: f1bae6b4c6253b6bc2e1b97aff4cf74e54a47ac47b679d3e04a0f0067d53fe24
Tx public key: 962bc82208e707e4a9bc9e3494fbcf852a49ef1510a0d95d5fd63b8b60d7909a
Timestamp: 1750508893 Timestamp [UCT]: 2025-06-21 12:28:13 Age [y:d:h:m:s]: 00:149:10:34:55
Block: 1309750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104654 RingCT/type: yes/0
Extra: 01962bc82208e707e4a9bc9e3494fbcf852a49ef1510a0d95d5fd63b8b60d7909a02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a4c0f38530c704f7f4a2640249e42190cfdf215898a7d1773a2d781053f10f7 0.600000000000 1797367 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": 1309760, "vin": [ { "gen": { "height": 1309750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a4c0f38530c704f7f4a2640249e42190cfdf215898a7d1773a2d781053f10f7" } } ], "extra": [ 1, 150, 43, 200, 34, 8, 231, 7, 228, 169, 188, 158, 52, 148, 251, 207, 133, 42, 73, 239, 21, 16, 160, 217, 93, 95, 214, 59, 139, 96, 215, 144, 154, 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