Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3660a372feaad42cc40643d4efbb7757a28201ce2cd1107e3aecbf7849134fa

Tx prefix hash: ee007171910b05ed40de7df7f241bcccda5eafe18e67b0ef0c0a71b0ee9533ce
Tx public key: 630152111d59f4585d22479fb7a045338812f8e475e5fd49f73b92e2709647e6
Timestamp: 1696510506 Timestamp [UCT]: 2023-10-05 12:55:06 Age [y:d:h:m:s]: 01:188:09:54:47
Block: 863013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395706 RingCT/type: yes/0
Extra: 01630152111d59f4585d22479fb7a045338812f8e475e5fd49f73b92e2709647e6021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.848163765000 dcy

stealth address amount amount idx
00: 4c63db4e06ebb5b87ccd7e61dafd19d64f2b52102fe03a6edee4b5a9daf791a6 0.848163765000 1317461 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": 863023, "vin": [ { "gen": { "height": 863013 } } ], "vout": [ { "amount": 848163765, "target": { "key": "4c63db4e06ebb5b87ccd7e61dafd19d64f2b52102fe03a6edee4b5a9daf791a6" } } ], "extra": [ 1, 99, 1, 82, 17, 29, 89, 244, 88, 93, 34, 71, 159, 183, 160, 69, 51, 136, 18, 248, 228, 117, 229, 253, 73, 247, 59, 146, 226, 112, 150, 71, 230, 2, 17, 0, 0, 0, 1, 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