Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f0b96fa12f429551897953ed6731522610cf3f58ea1d50d78de97cc270617bd

Tx prefix hash: 020140672574436d4b117164bf49ce7399ae7f0c2203ecbbdda448618d73a552
Tx public key: 433693177f9c139150e43a8e22fdd3a6e2c7da1fd1b2aeec2cf1d8acbaeffc8b
Timestamp: 1706664613 Timestamp [UCT]: 2024-01-31 01:30:13 Age [y:d:h:m:s]: 01:107:19:45:59
Block: 946974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338164 RingCT/type: yes/0
Extra: 01433693177f9c139150e43a8e22fdd3a6e2c7da1fd1b2aeec2cf1d8acbaeffc8b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e38ec1cd620f7deb2cb2b9fe2d52d5c959c258c537a6ddaa28188c6c8194b502 0.600000000000 1405320 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": 946984, "vin": [ { "gen": { "height": 946974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e38ec1cd620f7deb2cb2b9fe2d52d5c959c258c537a6ddaa28188c6c8194b502" } } ], "extra": [ 1, 67, 54, 147, 23, 127, 156, 19, 145, 80, 228, 58, 142, 34, 253, 211, 166, 226, 199, 218, 31, 209, 178, 174, 236, 44, 241, 216, 172, 186, 239, 252, 139, 2, 17, 0, 0, 0, 2, 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