Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768a03c4ba38f5e5c63aea6edb36fde6d31ca446ad5e315262301c52b1ab5f7b

Tx prefix hash: b0653fd4444398fb043ebb2d2ca5569aa589d5489c4ab03d07148cf94b8749f4
Tx public key: 64f04325b3030872eea2709d95f42fdfdc9c8728300b40231a1ce3045729415a
Timestamp: 1741730459 Timestamp [UCT]: 2025-03-11 22:00:59 Age [y:d:h:m:s]: 00:252:16:13:52
Block: 1237251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178320 RingCT/type: yes/0
Extra: 0164f04325b3030872eea2709d95f42fdfdc9c8728300b40231a1ce3045729415a021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f8a4b556541b5b243f1ad318bae8dc8324a66052fa319e5e778b8a8bfb9c61e 0.600000000000 1724206 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": 1237261, "vin": [ { "gen": { "height": 1237251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f8a4b556541b5b243f1ad318bae8dc8324a66052fa319e5e778b8a8bfb9c61e" } } ], "extra": [ 1, 100, 240, 67, 37, 179, 3, 8, 114, 238, 162, 112, 157, 149, 244, 47, 223, 220, 156, 135, 40, 48, 11, 64, 35, 26, 28, 227, 4, 87, 41, 65, 90, 2, 17, 0, 0, 0, 8, 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