Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba7f83653e977d3aace63445485c5d46a46886c55bce116e001042b1aafd0fb2

Tx prefix hash: 02f6c193eaec08c133c1815df816015d79bfd438b2d6a989df6e48cf8b29769f
Tx public key: 3c9af09485560e0aa12bf5239e6d3da88171ea1af8bbfe2711271010ffd22cbb
Timestamp: 1583239607 Timestamp [UCT]: 2020-03-03 12:46:47 Age [y:d:h:m:s]: 05:242:20:11:00
Block: 75732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1326094 RingCT/type: yes/0
Extra: 013c9af09485560e0aa12bf5239e6d3da88171ea1af8bbfe2711271010ffd22cbb02110000007256c366d3000000000000000000

1 output(s) for total of 344.404837056000 dcy

stealth address amount amount idx
00: a3868e3014e2d292ac2e17ed6dcb773611557943a998ee992bf4e7d293e5c03c 344.404837056000 139702 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": 75742, "vin": [ { "gen": { "height": 75732 } } ], "vout": [ { "amount": 344404837056, "target": { "key": "a3868e3014e2d292ac2e17ed6dcb773611557943a998ee992bf4e7d293e5c03c" } } ], "extra": [ 1, 60, 154, 240, 148, 133, 86, 14, 10, 161, 43, 245, 35, 158, 109, 61, 168, 129, 113, 234, 26, 248, 187, 254, 39, 17, 39, 16, 16, 255, 210, 44, 187, 2, 17, 0, 0, 0, 114, 86, 195, 102, 211, 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