Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42a09827d6ed7275098292b392cca19cbaf2efa28473ac290def9006670918f9

Tx prefix hash: 0aac816d4d1c48a85838a36609f26408efbac27aa362e736879006070d4ea207
Tx public key: 249250217b5a20ec522c41f4cc57162d32c3eade685b1cd81e825c32e26909e0
Timestamp: 1695646870 Timestamp [UCT]: 2023-09-25 13:01:10 Age [y:d:h:m:s]: 01:206:06:09:28
Block: 855854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408487 RingCT/type: yes/0
Extra: 01249250217b5a20ec522c41f4cc57162d32c3eade685b1cd81e825c32e26909e0021100000002faf35c9c000000000000000000

1 output(s) for total of 0.895778149000 dcy

stealth address amount amount idx
00: adcbce47ecf2916c5cc23b1e2d96e247b0d24c5ef2f80cd9c6dc7d5b234b910f 0.895778149000 1309902 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": 855864, "vin": [ { "gen": { "height": 855854 } } ], "vout": [ { "amount": 895778149, "target": { "key": "adcbce47ecf2916c5cc23b1e2d96e247b0d24c5ef2f80cd9c6dc7d5b234b910f" } } ], "extra": [ 1, 36, 146, 80, 33, 123, 90, 32, 236, 82, 44, 65, 244, 204, 87, 22, 45, 50, 195, 234, 222, 104, 91, 28, 216, 30, 130, 92, 50, 226, 105, 9, 224, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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