Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6786c75e9d57ced3bcd6f627accf7e9378cfe4cea068c098608763d34e21e2c

Tx prefix hash: b67bba711d3e5edd377d63952760929ce6957d39e637869e4a1d5b9d2291176f
Tx public key: 2f599ffd87f6beb05f0ff8ca5a4a41dcd73d45d2feda480d3734d6e6bf3a2c6b
Timestamp: 1719802267 Timestamp [UCT]: 2024-07-01 02:51:07 Age [y:d:h:m:s]: 00:290:09:29:24
Block: 1055910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207506 RingCT/type: yes/0
Extra: 012f599ffd87f6beb05f0ff8ca5a4a41dcd73d45d2feda480d3734d6e6bf3a2c6b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f80a1fa8e9841a0b559cc4c0f003a5bdcb66274f5ca26e70fbabb38838fc1fd 0.600000000000 1526317 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": 1055920, "vin": [ { "gen": { "height": 1055910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f80a1fa8e9841a0b559cc4c0f003a5bdcb66274f5ca26e70fbabb38838fc1fd" } } ], "extra": [ 1, 47, 89, 159, 253, 135, 246, 190, 176, 95, 15, 248, 202, 90, 74, 65, 220, 215, 61, 69, 210, 254, 218, 72, 13, 55, 52, 214, 230, 191, 58, 44, 107, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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