Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a17d3534a334e69aee53a2def938ae858c6e75eaa98ef8c59546790bdb992fc6

Tx prefix hash: 955c0f37cabece7c67c6d7e22fb7f2e0183e2420fd22841483a145b1c359587e
Tx public key: 26a2a150737ad5e4a1259d40b3a2867d0836be3719672ab33f8e6bf9a77113a5
Timestamp: 1744017401 Timestamp [UCT]: 2025-04-07 09:16:41 Age [y:d:h:m:s]: 00:228:14:14:23
Block: 1256165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161115 RingCT/type: yes/0
Extra: 0126a2a150737ad5e4a1259d40b3a2867d0836be3719672ab33f8e6bf9a77113a50211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b263aecbab812de3954c0d83955a234e40f2474b86e5bbed7655b68a061bd0b5 0.600000000000 1743278 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": 1256175, "vin": [ { "gen": { "height": 1256165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b263aecbab812de3954c0d83955a234e40f2474b86e5bbed7655b68a061bd0b5" } } ], "extra": [ 1, 38, 162, 161, 80, 115, 122, 213, 228, 161, 37, 157, 64, 179, 162, 134, 125, 8, 54, 190, 55, 25, 103, 42, 179, 63, 142, 107, 249, 167, 113, 19, 165, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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