Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 798a5d8c60b5431212f71070b662f5f29a1bcece8703f4e6c227ebc11f73f0fb

Tx prefix hash: ed0bfccdc700707f253c617081eeaaa40d30f255e9d0e64e65cda102c96c5d65
Tx public key: f4e83c1112928fab95a844d3dbd3423dd92bc273f83864b5b95868863c7acdc1
Timestamp: 1696031806 Timestamp [UCT]: 2023-09-29 23:56:46 Age [y:d:h:m:s]: 01:208:16:40:49
Block: 859053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410221 RingCT/type: yes/0
Extra: 01f4e83c1112928fab95a844d3dbd3423dd92bc273f83864b5b95868863c7acdc102110000000f4b8f5122000000000000000000

1 output(s) for total of 0.874179956000 dcy

stealth address amount amount idx
00: f9c77669c1c9f6f3f2b8400959732976981893eeb5a546714933935c068a243a 0.874179956000 1313261 of 0

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": 859063, "vin": [ { "gen": { "height": 859053 } } ], "vout": [ { "amount": 874179956, "target": { "key": "f9c77669c1c9f6f3f2b8400959732976981893eeb5a546714933935c068a243a" } } ], "extra": [ 1, 244, 232, 60, 17, 18, 146, 143, 171, 149, 168, 68, 211, 219, 211, 66, 61, 217, 43, 194, 115, 248, 56, 100, 181, 185, 88, 104, 134, 60, 122, 205, 193, 2, 17, 0, 0, 0, 15, 75, 143, 81, 34, 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