Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ea8bbe851eb74264a12cc838bdeb23d2edfde0dc09667d28e5ad46ebf9c9f3

Tx prefix hash: 984ac307a3e85c3251eba0ac6bb41f9dcb4b71d751f6e0e99eb991d9f0dd3e42
Tx public key: 3dd2e4cb7cf8b0958d5bc79c5b95d8af130ca17d625bc419a031864cbfeb729d
Timestamp: 1714998349 Timestamp [UCT]: 2024-05-06 12:25:49 Age [y:d:h:m:s]: 00:346:00:18:05
Block: 1016086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247337 RingCT/type: yes/0
Extra: 013dd2e4cb7cf8b0958d5bc79c5b95d8af130ca17d625bc419a031864cbfeb729d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96054d8c738d49a030079b57d6e114ffe655550533a5a57b86c057a5a4e9c532 0.600000000000 1479573 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": 1016096, "vin": [ { "gen": { "height": 1016086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96054d8c738d49a030079b57d6e114ffe655550533a5a57b86c057a5a4e9c532" } } ], "extra": [ 1, 61, 210, 228, 203, 124, 248, 176, 149, 141, 91, 199, 156, 91, 149, 216, 175, 19, 12, 161, 125, 98, 91, 196, 25, 160, 49, 134, 76, 191, 235, 114, 157, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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