Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33d4c836610c3d82e2f48553bd3ad188ef4774fd000a6b97c2b7c03007157a24

Tx prefix hash: 486be00fca31113ba4e3ccd155f618e038b5435f3380b38e44d28bd52b76cc30
Tx public key: d833f0f73d9d66c900917c33694e856ece4aeaf57c7971aa2b58fdfada6cee29
Timestamp: 1715483154 Timestamp [UCT]: 2024-05-12 03:05:54 Age [y:d:h:m:s]: 00:355:21:04:36
Block: 1020138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254363 RingCT/type: yes/0
Extra: 01d833f0f73d9d66c900917c33694e856ece4aeaf57c7971aa2b58fdfada6cee2902110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad07f85f2626334cdadb8cb814acb8012fe5a0404776eaebe929da8d89c935be 0.600000000000 1484197 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": 1020148, "vin": [ { "gen": { "height": 1020138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad07f85f2626334cdadb8cb814acb8012fe5a0404776eaebe929da8d89c935be" } } ], "extra": [ 1, 216, 51, 240, 247, 61, 157, 102, 201, 0, 145, 124, 51, 105, 78, 133, 110, 206, 74, 234, 245, 124, 121, 113, 170, 43, 88, 253, 250, 218, 108, 238, 41, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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