Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 650d5f37a025e669c6e44caee69a6c72495c349fc01b6cb7679d0b63ea9cdd1b

Tx prefix hash: f70ab262b324be3df2e1cd97c31927d27e45c8448bcd48dbfa7044cf66c2ba02
Tx public key: 9ffbe34ea182bca870ca120ed7300ae4265536c4c0e765ea7e01b711c999b051
Timestamp: 1732634019 Timestamp [UCT]: 2024-11-26 15:13:39 Age [y:d:h:m:s]: 00:153:08:42:18
Block: 1162196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109444 RingCT/type: yes/0
Extra: 019ffbe34ea182bca870ca120ed7300ae4265536c4c0e765ea7e01b711c999b051021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e07e429e74cb77622d1779f618b21cab8d8d79041e7da75e693dcef56c862266 0.600000000000 1647851 of 15

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": 1162206, "vin": [ { "gen": { "height": 1162196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e07e429e74cb77622d1779f618b21cab8d8d79041e7da75e693dcef56c862266" } } ], "extra": [ 1, 159, 251, 227, 78, 161, 130, 188, 168, 112, 202, 18, 14, 215, 48, 10, 228, 38, 85, 54, 196, 192, 231, 101, 234, 126, 1, 183, 17, 201, 153, 176, 81, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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