Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee8c4fdb99af17b44468c8491f634cd9543988d2e7f93aa8d026d74d7f06e1de

Tx prefix hash: 0d5e5634e6da8721b924f9b89a683b9cb231233cbeaa14625c91de4e228f42ae
Tx public key: c5167ed62fdb0673aa41c60f0bb254de9dfafa556128276b7220373b17465080
Timestamp: 1582431271 Timestamp [UCT]: 2020-02-23 04:14:31 Age [y:d:h:m:s]: 04:344:21:37:06
Block: 70508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138955 RingCT/type: yes/0
Extra: 01c5167ed62fdb0673aa41c60f0bb254de9dfafa556128276b7220373b17465080021100000001c71d3ff9000000000000000000

1 output(s) for total of 358.408688863000 dcy

stealth address amount amount idx
00: a2157a20a70bcef6c1a77981b2020865ba3d5220ca7d8ea1b3b175b61ab98ec6 358.408688863000 130320 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": 70518, "vin": [ { "gen": { "height": 70508 } } ], "vout": [ { "amount": 358408688863, "target": { "key": "a2157a20a70bcef6c1a77981b2020865ba3d5220ca7d8ea1b3b175b61ab98ec6" } } ], "extra": [ 1, 197, 22, 126, 214, 47, 219, 6, 115, 170, 65, 198, 15, 11, 178, 84, 222, 157, 250, 250, 85, 97, 40, 39, 107, 114, 32, 55, 59, 23, 70, 80, 128, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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