Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a83352b059ebd579bd87abd8ca5a8b4255e48ad39ce4edfe8c4c388b966d61

Tx prefix hash: fbb13da7210755fc86baea9431ff3a815a3828d17e7ebe6a9ed6a2ebfa545358
Tx public key: 03d88750dbf0ae9059e6946b2804e81c9157e70eeb0dfa7f4a10c306b92c4395
Timestamp: 1713500477 Timestamp [UCT]: 2024-04-19 04:21:17 Age [y:d:h:m:s]: 01:034:11:26:59
Block: 1003665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285611 RingCT/type: yes/0
Extra: 0103d88750dbf0ae9059e6946b2804e81c9157e70eeb0dfa7f4a10c306b92c4395021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89c6ea4f1d8202e051f6853142685f2cd1318546e2701c1f8215b157375f5868 0.600000000000 1464207 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": 1003675, "vin": [ { "gen": { "height": 1003665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89c6ea4f1d8202e051f6853142685f2cd1318546e2701c1f8215b157375f5868" } } ], "extra": [ 1, 3, 216, 135, 80, 219, 240, 174, 144, 89, 230, 148, 107, 40, 4, 232, 28, 145, 87, 231, 14, 235, 13, 250, 127, 74, 16, 195, 6, 185, 44, 67, 149, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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