Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30e6ffc0ebb80f1bd8b4ec6b0f3a445a7d9dac38a2e6646a11c15bbb14ab920a

Tx prefix hash: 5883f6c8ffc8dcdc0c6d5d7c9278a8970c6c170c05a72c9276766ba4401e5733
Tx public key: 65eead7081c985fba7212bea04b4c63f84d2fadc8096dcde4e1dfb81577dd741
Timestamp: 1657444039 Timestamp [UCT]: 2022-07-10 09:07:19 Age [y:d:h:m:s]: 02:309:05:10:14
Block: 540643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742158 RingCT/type: yes/0
Extra: 0165eead7081c985fba7212bea04b4c63f84d2fadc8096dcde4e1dfb81577dd741021100000002c9067537000000000000000000

1 output(s) for total of 9.922599337000 dcy

stealth address amount amount idx
00: 69b04190d821f58f5dee777755b0ae727d08b7de3f1c7af540132e37178edbf1 9.922599337000 970900 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": 540653, "vin": [ { "gen": { "height": 540643 } } ], "vout": [ { "amount": 9922599337, "target": { "key": "69b04190d821f58f5dee777755b0ae727d08b7de3f1c7af540132e37178edbf1" } } ], "extra": [ 1, 101, 238, 173, 112, 129, 201, 133, 251, 167, 33, 43, 234, 4, 180, 198, 63, 132, 210, 250, 220, 128, 150, 220, 222, 78, 29, 251, 129, 87, 125, 215, 65, 2, 17, 0, 0, 0, 2, 201, 6, 117, 55, 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