Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c52b7eec60f347d9b18e3a90bf303053f0a557125a2994f7066a88e6978bf71f

Tx prefix hash: 45bbf272f737a60293cb426771069fea121671e0bc691e35a8e41e11d351d41b
Tx public key: d9da0898f1197c3568c535a3b654a84c09bc667edff57ae491ede1c2b960114c
Timestamp: 1723932937 Timestamp [UCT]: 2024-08-17 22:15:37 Age [y:d:h:m:s]: 01:083:02:41:19
Block: 1090166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317848 RingCT/type: yes/0
Extra: 01d9da0898f1197c3568c535a3b654a84c09bc667edff57ae491ede1c2b960114c02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e28f0cc76784f1ec7fd9c287bfc4f7461b1e65a568d6b42f3628f1a94e6d8fc4 0.600000000000 1564789 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": 1090176, "vin": [ { "gen": { "height": 1090166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e28f0cc76784f1ec7fd9c287bfc4f7461b1e65a568d6b42f3628f1a94e6d8fc4" } } ], "extra": [ 1, 217, 218, 8, 152, 241, 25, 124, 53, 104, 197, 53, 163, 182, 84, 168, 76, 9, 188, 102, 126, 223, 245, 122, 228, 145, 237, 225, 194, 185, 96, 17, 76, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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