Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3495d8073352524577c6dd4e454379d96651c86b9f5b0a6aaeec3d66b1e9dc1

Tx prefix hash: d321ceda21efd70d8faeb3b78e30cc39e8d226aee7536c8ecf4ca4dc5c2f3f65
Tx public key: 1be4d7be395ebf4ab3708c3aa8029039b9c4d0a50edc1dac17da88dfa348e9e9
Timestamp: 1748470472 Timestamp [UCT]: 2025-05-28 22:14:32 Age [y:d:h:m:s]: 00:209:06:28:51
Block: 1293048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147302 RingCT/type: yes/0
Extra: 011be4d7be395ebf4ab3708c3aa8029039b9c4d0a50edc1dac17da88dfa348e9e9021100000001df096e52000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0ae1f82962096f7fc143daa856e2444e8abb804a3ef7dee4b41173905496d80 0.600000000000 1780519 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": 1293058, "vin": [ { "gen": { "height": 1293048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0ae1f82962096f7fc143daa856e2444e8abb804a3ef7dee4b41173905496d80" } } ], "extra": [ 1, 27, 228, 215, 190, 57, 94, 191, 74, 179, 112, 140, 58, 168, 2, 144, 57, 185, 196, 208, 165, 14, 220, 29, 172, 23, 218, 136, 223, 163, 72, 233, 233, 2, 17, 0, 0, 0, 1, 223, 9, 110, 82, 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