Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 281dea1b7ea48bda3cb8962d73d1451f8f736f5847317060cb49d500a4792a19

Tx prefix hash: c7c7a5d5dcc555c9b9635d336af7966967344998e75c987170177fc5ea392d8a
Tx public key: 718fbda4362adf4fc526dd5801012844a790d07fc2637ce82bfc6a834de5372a
Timestamp: 1696684488 Timestamp [UCT]: 2023-10-07 13:14:48 Age [y:d:h:m:s]: 01:171:23:49:56
Block: 864461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383953 RingCT/type: yes/0
Extra: 01718fbda4362adf4fc526dd5801012844a790d07fc2637ce82bfc6a834de5372a021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.838845323000 dcy

stealth address amount amount idx
00: d44bc646baf1b27c874f4317826d37b005418cef60d7e6a1e9f46e7b13c76b1a 0.838845323000 1318975 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": 864471, "vin": [ { "gen": { "height": 864461 } } ], "vout": [ { "amount": 838845323, "target": { "key": "d44bc646baf1b27c874f4317826d37b005418cef60d7e6a1e9f46e7b13c76b1a" } } ], "extra": [ 1, 113, 143, 189, 164, 54, 42, 223, 79, 197, 38, 221, 88, 1, 1, 40, 68, 167, 144, 208, 127, 194, 99, 124, 232, 43, 252, 106, 131, 77, 229, 55, 42, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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