Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 647371d9918fa9a9620bd4362086396b752207b7871abc0ab063d2cc746163c3

Tx prefix hash: cc8fa4f6a3c728279918f2fb21b1dd6ec436dc2472cb210f524826cb388dedb2
Tx public key: a00a4ca23ed18e7024a49ad86c81536bf7f3ad2bbf2b43176418f721bca6a9ce
Timestamp: 1730145861 Timestamp [UCT]: 2024-10-28 20:04:21 Age [y:d:h:m:s]: 00:157:06:40:26
Block: 1141596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112224 RingCT/type: yes/0
Extra: 01a00a4ca23ed18e7024a49ad86c81536bf7f3ad2bbf2b43176418f721bca6a9ce021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 058164e9cade76c42b6aa057d5d3898c815e5912fbc2e6f8966cfbae904ffe34 0.600000000000 1625405 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": 1141606, "vin": [ { "gen": { "height": 1141596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "058164e9cade76c42b6aa057d5d3898c815e5912fbc2e6f8966cfbae904ffe34" } } ], "extra": [ 1, 160, 10, 76, 162, 62, 209, 142, 112, 36, 164, 154, 216, 108, 129, 83, 107, 247, 243, 173, 43, 191, 43, 67, 23, 100, 24, 247, 33, 188, 166, 169, 206, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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