Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e26277ea4819f106374a7fe4c81739504e5b3e71ff3e387e6996174d60e3a0c4

Tx prefix hash: 244a30af2dec74e370828a9ae8ca1c8b1ab537f562a5832aae6cbbe226f38175
Tx public key: 107c4ac54d4815ceb6710a410cd3a13aa2a3bfe5bb8ab088ea741893f69ba52a
Timestamp: 1732339314 Timestamp [UCT]: 2024-11-23 05:21:54 Age [y:d:h:m:s]: 00:001:01:31:04
Block: 1159754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 763 RingCT/type: yes/0
Extra: 01107c4ac54d4815ceb6710a410cd3a13aa2a3bfe5bb8ab088ea741893f69ba52a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c6a798960e05cb4e0dce3d0cba248a4254006d8bd433757e82accad6ac19229 0.600000000000 1645393 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": 1159764, "vin": [ { "gen": { "height": 1159754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c6a798960e05cb4e0dce3d0cba248a4254006d8bd433757e82accad6ac19229" } } ], "extra": [ 1, 16, 124, 74, 197, 77, 72, 21, 206, 182, 113, 10, 65, 12, 211, 161, 58, 162, 163, 191, 229, 187, 138, 176, 136, 234, 116, 24, 147, 246, 155, 165, 42, 2, 17, 0, 0, 0, 5, 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