Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be2f04ad31c898f72fca7c6ea76649e9817afcafb3d34d2c49eaeded6f2f49d7

Tx prefix hash: 58d2486ab40cdfb46eb28df94c2f21e198cb7d424e17c15c46a6c0f33317e9c4
Tx public key: 170d78e085fbd26b8f94aa0fd5bbe5669ec5c429f9c34d324da08f23f8e84f40
Timestamp: 1717142496 Timestamp [UCT]: 2024-05-31 08:01:36 Age [y:d:h:m:s]: 00:285:16:37:14
Block: 1033873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204176 RingCT/type: yes/0
Extra: 01170d78e085fbd26b8f94aa0fd5bbe5669ec5c429f9c34d324da08f23f8e84f4002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee50bff18cf8fdf7c4ca1abe1198b6de1688a718189c7e3a3dbab46065804c69 0.600000000000 1502346 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": 1033883, "vin": [ { "gen": { "height": 1033873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee50bff18cf8fdf7c4ca1abe1198b6de1688a718189c7e3a3dbab46065804c69" } } ], "extra": [ 1, 23, 13, 120, 224, 133, 251, 210, 107, 143, 148, 170, 15, 213, 187, 229, 102, 158, 197, 196, 41, 249, 195, 77, 50, 77, 160, 143, 35, 248, 232, 79, 64, 2, 17, 0, 0, 0, 1, 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