Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0041a0aba53595d155ba495b98f0f1570bcbe14556d968967e57803bf93dc7ce

Tx prefix hash: 909c4d6322a64a6424a4d22abc9f2acaa78f0ae0bcae4e824f4db34bd5d5510b
Tx public key: 5b169163ff09f7bc1e57e6c6b964131e9e506322675d94fd7b33770eeee9d9e0
Timestamp: 1742101081 Timestamp [UCT]: 2025-03-16 04:58:01 Age [y:d:h:m:s]: 00:256:08:26:09
Block: 1240329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180950 RingCT/type: yes/0
Extra: 015b169163ff09f7bc1e57e6c6b964131e9e506322675d94fd7b33770eeee9d9e0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e2c47ef12e551736716521e34fc6b1b8586f2a8c7f2ec0ba485a7545f5c9d34 0.600000000000 1727294 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": 1240339, "vin": [ { "gen": { "height": 1240329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e2c47ef12e551736716521e34fc6b1b8586f2a8c7f2ec0ba485a7545f5c9d34" } } ], "extra": [ 1, 91, 22, 145, 99, 255, 9, 247, 188, 30, 87, 230, 198, 185, 100, 19, 30, 158, 80, 99, 34, 103, 93, 148, 253, 123, 51, 119, 14, 238, 233, 217, 224, 2, 17, 0, 0, 0, 3, 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