Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd40278081af17d97670cc6170f4271b64fdd231a0827a3859ff110c40695b17

Tx prefix hash: ac75b35ba1b954e3e04fc8e9cc7b812e70cdb7bfc4f607c28a0c097433a3396f
Tx public key: 7a5e2e42f03d861dc74382f14f4f5a60a0d3a6d99ef8cd96b5f1a2464b343c85
Timestamp: 1728964908 Timestamp [UCT]: 2024-10-15 04:01:48 Age [y:d:h:m:s]: 00:193:16:53:14
Block: 1131875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138239 RingCT/type: yes/0
Extra: 017a5e2e42f03d861dc74382f14f4f5a60a0d3a6d99ef8cd96b5f1a2464b343c85021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e49e2833a241426b121d9b6e83ad95913a7e18e63b400d86d75d8dbe1f795105 0.600000000000 1614784 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": 1131885, "vin": [ { "gen": { "height": 1131875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e49e2833a241426b121d9b6e83ad95913a7e18e63b400d86d75d8dbe1f795105" } } ], "extra": [ 1, 122, 94, 46, 66, 240, 61, 134, 29, 199, 67, 130, 241, 79, 79, 90, 96, 160, 211, 166, 217, 158, 248, 205, 150, 181, 241, 162, 70, 75, 52, 60, 133, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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