Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ab302943ada8ee684ea35aac694c9c4272d86467fadc503d21fd1d71898019

Tx prefix hash: 4c1df2ef843fede0a16ca230ec713d3a45fa6b3dbb29dfd637c0bd95b3dd7369
Tx public key: 26a8eae84e37e627910d39c50934cb1bc800984e026275777b14c229ba52e1eb
Timestamp: 1728675088 Timestamp [UCT]: 2024-10-11 19:31:28 Age [y:d:h:m:s]: 00:153:16:48:20
Block: 1129479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109644 RingCT/type: yes/0
Extra: 0126a8eae84e37e627910d39c50934cb1bc800984e026275777b14c229ba52e1eb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be288f9fbe2d6586fce304e000f98d241bac4993b4c8dfa6c5e2f7098c6e5999 0.600000000000 1612306 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": 1129489, "vin": [ { "gen": { "height": 1129479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be288f9fbe2d6586fce304e000f98d241bac4993b4c8dfa6c5e2f7098c6e5999" } } ], "extra": [ 1, 38, 168, 234, 232, 78, 55, 230, 39, 145, 13, 57, 197, 9, 52, 203, 27, 200, 0, 152, 78, 2, 98, 117, 119, 123, 20, 194, 41, 186, 82, 225, 235, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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