Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b72cbde40e9f7c36097c3b13b0b90798a31785b0b73cff36ed9eb1e0a84f290e

Tx prefix hash: 57747671a2b4daa4635e76d40d560036789a9d20172e747a930421b8b33d2a5c
Tx public key: e190c712acc6c0dec5357633fe563cb5385aadc97c596b1980e261e089cd3762
Timestamp: 1737231746 Timestamp [UCT]: 2025-01-18 20:22:26 Age [y:d:h:m:s]: 00:337:07:30:09
Block: 1200226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238668 RingCT/type: yes/0
Extra: 01e190c712acc6c0dec5357633fe563cb5385aadc97c596b1980e261e089cd3762021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d3e0808c7fdba3451f9a383ce11191e611d9f8341cf237b9bf873e4586b814 0.600000000000 1686869 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": 1200236, "vin": [ { "gen": { "height": 1200226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d3e0808c7fdba3451f9a383ce11191e611d9f8341cf237b9bf873e4586b814" } } ], "extra": [ 1, 225, 144, 199, 18, 172, 198, 192, 222, 197, 53, 118, 51, 254, 86, 60, 181, 56, 90, 173, 201, 124, 89, 107, 25, 128, 226, 97, 224, 137, 205, 55, 98, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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