Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e42610463d0a4f2901baca90f01bc51474c7e9b86f338eb732c8867cf7ef8f26

Tx prefix hash: 7827682a016ea08f4d5fc4f037878cffb003d940da37c421623fd22625e39b06
Tx public key: 1f2b814d6f5bced5cfed5185b01a3ebfc8309702f7c03fa575b40db0f0f1d73b
Timestamp: 1714256243 Timestamp [UCT]: 2024-04-27 22:17:23 Age [y:d:h:m:s]: 00:337:02:28:12
Block: 1009934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240979 RingCT/type: yes/0
Extra: 011f2b814d6f5bced5cfed5185b01a3ebfc8309702f7c03fa575b40db0f0f1d73b02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1c841a356539f40737659127113131e6fa2110964c5554dc5b425ca14f83f4f 0.600000000000 1471744 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": 1009944, "vin": [ { "gen": { "height": 1009934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1c841a356539f40737659127113131e6fa2110964c5554dc5b425ca14f83f4f" } } ], "extra": [ 1, 31, 43, 129, 77, 111, 91, 206, 213, 207, 237, 81, 133, 176, 26, 62, 191, 200, 48, 151, 2, 247, 192, 63, 165, 117, 180, 13, 176, 240, 241, 215, 59, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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