Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba1ba46b706531902acad7e5292777295ee095699ffe79b7106aa82dbf0f7a45

Tx prefix hash: 6f85d4330c4666afedeae8953e65d9951af33fd3c2044876c04d5ba8cfc3371b
Tx public key: 6fea0f99d4edb565d64fb91dcd59e8b6fea48ef7bd01081d90e4d8b57b15b0c3
Timestamp: 1610056542 Timestamp [UCT]: 2021-01-07 21:55:42 Age [y:d:h:m:s]: 03:323:11:42:13
Block: 175975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 986050 RingCT/type: yes/0
Extra: 016fea0f99d4edb565d64fb91dcd59e8b6fea48ef7bd01081d90e4d8b57b15b0c302110000005d90ce5c0f000000000000000000

1 output(s) for total of 160.295906308000 dcy

stealth address amount amount idx
00: a2d1c4e8e37649b324dea44e7809f8ba030faa5ea954d71c7d6d762329a160c3 160.295906308000 336645 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": 175985, "vin": [ { "gen": { "height": 175975 } } ], "vout": [ { "amount": 160295906308, "target": { "key": "a2d1c4e8e37649b324dea44e7809f8ba030faa5ea954d71c7d6d762329a160c3" } } ], "extra": [ 1, 111, 234, 15, 153, 212, 237, 181, 101, 214, 79, 185, 29, 205, 89, 232, 182, 254, 164, 142, 247, 189, 1, 8, 29, 144, 228, 216, 181, 123, 21, 176, 195, 2, 17, 0, 0, 0, 93, 144, 206, 92, 15, 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