Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33961f895d0de1c3b89b18a9e1ffff962908d2282a25d8751994b44fcdc5ec50

Tx prefix hash: 482035a258de5ba6740b3909d43352447919bae214fd6ab8ebe69d3340ee4862
Tx public key: 8deffdf6b6a7f9ba01373913c6b692d817d59b9a26d4619e92a09fae7809bf67
Timestamp: 1711009276 Timestamp [UCT]: 2024-03-21 08:21:16 Age [y:d:h:m:s]: 00:361:20:49:22
Block: 983042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258717 RingCT/type: yes/0
Extra: 018deffdf6b6a7f9ba01373913c6b692d817d59b9a26d4619e92a09fae7809bf6702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0387b3c341df34f0a737672e3a2e2004af1f552e9e873b14167bb0323316ba66 0.600000000000 1443161 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": 983052, "vin": [ { "gen": { "height": 983042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0387b3c341df34f0a737672e3a2e2004af1f552e9e873b14167bb0323316ba66" } } ], "extra": [ 1, 141, 239, 253, 246, 182, 167, 249, 186, 1, 55, 57, 19, 198, 182, 146, 216, 23, 213, 155, 154, 38, 212, 97, 158, 146, 160, 159, 174, 120, 9, 191, 103, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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