Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 509b531a91958f59279dfc0ba24f18a3c4294caaaa197cfe54882d34ebbf4ffd

Tx prefix hash: fb0e03a378b872fa79c2e6eb3feee3908e82089e09e3a209d9c88828362db650
Tx public key: 7497d635a091258cead60f91db3464aad6a806d6b9a12fdefae20c158b269a80
Timestamp: 1663995231 Timestamp [UCT]: 2022-09-24 04:53:51 Age [y:d:h:m:s]: 02:177:17:17:46
Block: 594577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 648418 RingCT/type: yes/0
Extra: 017497d635a091258cead60f91db3464aad6a806d6b9a12fdefae20c158b269a8002110000000575e3f0e9000000000000000000

1 output(s) for total of 6.575361676000 dcy

stealth address amount amount idx
00: e5fd4110d24df2159319edb0b12a873e2a1cae8c697474806bf81c45f1ad8252 6.575361676000 1029480 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": 594587, "vin": [ { "gen": { "height": 594577 } } ], "vout": [ { "amount": 6575361676, "target": { "key": "e5fd4110d24df2159319edb0b12a873e2a1cae8c697474806bf81c45f1ad8252" } } ], "extra": [ 1, 116, 151, 214, 53, 160, 145, 37, 140, 234, 214, 15, 145, 219, 52, 100, 170, 214, 168, 6, 214, 185, 161, 47, 222, 250, 226, 12, 21, 139, 38, 154, 128, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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