Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecd355627d72bd7b162d21d08f090be086f28dc56d1b8e461867ae4ebe8e441a

Tx prefix hash: cb0a5c5830743d95a6e9b8c563815ec1ebdbc34103496c0c68dbc234a2820a4f
Tx public key: e45d5209e946ecc28cac943d63264f382b7e9f3dffb58a2ef0a39890d474d45f
Timestamp: 1579155890 Timestamp [UCT]: 2020-01-16 06:24:50 Age [y:d:h:m:s]: 04:316:02:05:00
Block: 46611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115388 RingCT/type: yes/0
Extra: 01e45d5209e946ecc28cac943d63264f382b7e9f3dffb58a2ef0a39890d474d45f0211000000098a2ee0d9000000000000000000

1 output(s) for total of 430.089901847000 dcy

stealth address amount amount idx
00: 01d9d142663acc1bcce1a56d3350fbc5fe82c2b5d4faadc6b9a62944466181a3 430.089901847000 85824 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": 46621, "vin": [ { "gen": { "height": 46611 } } ], "vout": [ { "amount": 430089901847, "target": { "key": "01d9d142663acc1bcce1a56d3350fbc5fe82c2b5d4faadc6b9a62944466181a3" } } ], "extra": [ 1, 228, 93, 82, 9, 233, 70, 236, 194, 140, 172, 148, 61, 99, 38, 79, 56, 43, 126, 159, 61, 255, 181, 138, 46, 240, 163, 152, 144, 212, 116, 212, 95, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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