Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344005ce39513fe6ca3f547849fe1973343132bd8b953a1bcd0f129fa91e8d3a

Tx prefix hash: 733e0c779aae9acd1ccd6949de043e1ee9cba41e7354aa38aeb7484c55d4bf4b
Tx public key: 28146d21d64116621c72b91ac97699e9dd2c8b0d197f86e27cef6809510b8e1a
Timestamp: 1732938977 Timestamp [UCT]: 2024-11-30 03:56:17 Age [y:d:h:m:s]: 00:114:20:37:47
Block: 1164736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81871 RingCT/type: yes/0
Extra: 0128146d21d64116621c72b91ac97699e9dd2c8b0d197f86e27cef6809510b8e1a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9734e3049d18ba0c4a99e9574c2da499c281309ed350508a61f8c42fefda1c28 0.600000000000 1650411 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": 1164746, "vin": [ { "gen": { "height": 1164736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9734e3049d18ba0c4a99e9574c2da499c281309ed350508a61f8c42fefda1c28" } } ], "extra": [ 1, 40, 20, 109, 33, 214, 65, 22, 98, 28, 114, 185, 26, 201, 118, 153, 233, 221, 44, 139, 13, 25, 127, 134, 226, 124, 239, 104, 9, 81, 11, 142, 26, 2, 17, 0, 0, 0, 4, 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