Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747f964522652fb2b7a1355294a27caee050c0b90baf1396f237ae895a2e1ba5

Tx prefix hash: 0e93b4db3c64e5f164ca55d7218410c564616d7eb59c8cf838cbd398f4c9035f
Tx public key: a652dbce610727a272a859d2143af2f30bf4c6c3975d12d705905ad83d6894c3
Timestamp: 1697322628 Timestamp [UCT]: 2023-10-14 22:30:28 Age [y:d:h:m:s]: 01:172:08:45:18
Block: 869752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384219 RingCT/type: yes/0
Extra: 01a652dbce610727a272a859d2143af2f30bf4c6c3975d12d705905ad83d6894c302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.805657771000 dcy

stealth address amount amount idx
00: 001c585bb29e7a579170cc922ee194e1314e887339777cff4378a1d1e38e517e 0.805657771000 1324607 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": 869762, "vin": [ { "gen": { "height": 869752 } } ], "vout": [ { "amount": 805657771, "target": { "key": "001c585bb29e7a579170cc922ee194e1314e887339777cff4378a1d1e38e517e" } } ], "extra": [ 1, 166, 82, 219, 206, 97, 7, 39, 162, 114, 168, 89, 210, 20, 58, 242, 243, 11, 244, 198, 195, 151, 93, 18, 215, 5, 144, 90, 216, 61, 104, 148, 195, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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