Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7a49cc929da912481ac3ccb76d3aa771ab22266c4aa808be2bc5c64395c5f42

Tx prefix hash: b6c301f1c6e9a63307c5ad9057d2437d9a65f9180ddc6c13b97b311620794063
Tx public key: d6c3e34dd7551423377d5d4dfe90deec047ba9d3a453149669753cf19b346901
Timestamp: 1639138478 Timestamp [UCT]: 2021-12-10 12:14:38 Age [y:d:h:m:s]: 03:060:10:44:28
Block: 392480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 821910 RingCT/type: yes/0
Extra: 01d6c3e34dd7551423377d5d4dfe90deec047ba9d3a453149669753cf19b346901021100000001f6cc1430000000000000000000

1 output(s) for total of 30.729725911000 dcy

stealth address amount amount idx
00: b2960e3fa7812d7fbee0a64190da9a8105ba9a7eb7964e5a9a34d76b5b1d2585 30.729725911000 789365 of 0

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": 392490, "vin": [ { "gen": { "height": 392480 } } ], "vout": [ { "amount": 30729725911, "target": { "key": "b2960e3fa7812d7fbee0a64190da9a8105ba9a7eb7964e5a9a34d76b5b1d2585" } } ], "extra": [ 1, 214, 195, 227, 77, 215, 85, 20, 35, 55, 125, 93, 77, 254, 144, 222, 236, 4, 123, 169, 211, 164, 83, 20, 150, 105, 117, 60, 241, 155, 52, 105, 1, 2, 17, 0, 0, 0, 1, 246, 204, 20, 48, 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