Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8bca4c03a5ab549fb3efa5e6942a0c95b9f9f72f700de706a51332da5c0e258

Tx prefix hash: 1ec7cd4b3058b12fbbb1acff231f9e2fc2b4901ea3f9c4d1ea72978bc4518712
Tx public key: 7c15ced6527b134bec4c9f330847d63634aa78770486081c2a2cf2b0bbcc5738
Timestamp: 1697245263 Timestamp [UCT]: 2023-10-14 01:01:03 Age [y:d:h:m:s]: 01:098:20:50:26
Block: 869109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331879 RingCT/type: yes/0
Extra: 017c15ced6527b134bec4c9f330847d63634aa78770486081c2a2cf2b0bbcc573802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.809619812000 dcy

stealth address amount amount idx
00: b96e1d820a444fb2f3f6118c2bc46bae7580c81bcff5b64676c26b0e9a2941db 0.809619812000 1323944 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": 869119, "vin": [ { "gen": { "height": 869109 } } ], "vout": [ { "amount": 809619812, "target": { "key": "b96e1d820a444fb2f3f6118c2bc46bae7580c81bcff5b64676c26b0e9a2941db" } } ], "extra": [ 1, 124, 21, 206, 214, 82, 123, 19, 75, 236, 76, 159, 51, 8, 71, 214, 54, 52, 170, 120, 119, 4, 134, 8, 28, 42, 44, 242, 176, 187, 204, 87, 56, 2, 17, 0, 0, 0, 1, 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