Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa63239269df1a821dfd2b849ba39d216bb9e32cc566eb15d4d3f273bca5110f

Tx prefix hash: 9450419b43aba38dfb742a6a487169ce27b584a7dfa62270d97d1b636bf08d8f
Tx public key: efe5d2cfcdca0cba309100f5cbcd0ebdc3df10c77392b8c70383b5143cf436e6
Timestamp: 1675547191 Timestamp [UCT]: 2023-02-04 21:46:31 Age [y:d:h:m:s]: 02:023:22:38:20
Block: 689901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538695 RingCT/type: yes/0
Extra: 01efe5d2cfcdca0cba309100f5cbcd0ebdc3df10c77392b8c70383b5143cf436e60211000000045029cbac000000000000000000

1 output(s) for total of 3.177397310000 dcy

stealth address amount amount idx
00: da5b76a8fe188575817769d1577a017dd80e65e74c461c7e6de2780f8e2c38fb 3.177397310000 1132603 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": 689911, "vin": [ { "gen": { "height": 689901 } } ], "vout": [ { "amount": 3177397310, "target": { "key": "da5b76a8fe188575817769d1577a017dd80e65e74c461c7e6de2780f8e2c38fb" } } ], "extra": [ 1, 239, 229, 210, 207, 205, 202, 12, 186, 48, 145, 0, 245, 203, 205, 14, 189, 195, 223, 16, 199, 115, 146, 184, 199, 3, 131, 181, 20, 60, 244, 54, 230, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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