Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b671fe325ad898db0af0de57486dca942de0d2c79a6a5c9e26c7e99228210dc

Tx prefix hash: f62ae289d097615264eaffc519de3009d87d4b73fd1d1961f4cb32cd6f47df4d
Tx public key: 30b0c193d092b4541ca14c4990a7fd9469464b27922a3bb244466e36dad3b203
Timestamp: 1719281110 Timestamp [UCT]: 2024-06-25 02:05:10 Age [y:d:h:m:s]: 00:309:05:32:28
Block: 1051586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220997 RingCT/type: yes/0
Extra: 0130b0c193d092b4541ca14c4990a7fd9469464b27922a3bb244466e36dad3b2030211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eeabec1fd9d562622d19a186af3ad32eaa5c0aea368c26eb1c552fef9e974de2 0.600000000000 1521901 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": 1051596, "vin": [ { "gen": { "height": 1051586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eeabec1fd9d562622d19a186af3ad32eaa5c0aea368c26eb1c552fef9e974de2" } } ], "extra": [ 1, 48, 176, 193, 147, 208, 146, 180, 84, 28, 161, 76, 73, 144, 167, 253, 148, 105, 70, 75, 39, 146, 42, 59, 178, 68, 70, 110, 54, 218, 211, 178, 3, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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