Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 258a14ee79154ffc71863f9cbb2f13db8a29f0e8d136f8ed1c3bcdfda2c6248c

Tx prefix hash: 65fcde6c9bb6babfb5b4a894fa69e4c87ec5401a50ddf8301028ce5ad4bf1657
Tx public key: 442956bd5a3f178431a6052f6e1f7173a561afd5d4eac364a1e2d5202e47ef15
Timestamp: 1736750758 Timestamp [UCT]: 2025-01-13 06:45:58 Age [y:d:h:m:s]: 00:084:00:00:43
Block: 1196288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59806 RingCT/type: yes/0
Extra: 01442956bd5a3f178431a6052f6e1f7173a561afd5d4eac364a1e2d5202e47ef15021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7aa6782b9f49d873d70fbed0738b86de72107e8354daa782fc93908204b05c5 0.600000000000 1682885 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": 1196298, "vin": [ { "gen": { "height": 1196288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7aa6782b9f49d873d70fbed0738b86de72107e8354daa782fc93908204b05c5" } } ], "extra": [ 1, 68, 41, 86, 189, 90, 63, 23, 132, 49, 166, 5, 47, 110, 31, 113, 115, 165, 97, 175, 213, 212, 234, 195, 100, 161, 226, 213, 32, 46, 71, 239, 21, 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