Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78dcd254d787d197a558c8ddc5d689d0e7b3143076e575ef93d24f0c26875038

Tx prefix hash: 5a3405582a474789784183b5ce7dc9389f1696ee9e468bd8d2c7d4064a4b43b8
Tx public key: fa8641d904325f52d0652a796051f7f9226a92c06ff8d3eacd87e56986814ca2
Timestamp: 1576639681 Timestamp [UCT]: 2019-12-18 03:28:01 Age [y:d:h:m:s]: 05:012:19:38:32
Block: 28012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157315 RingCT/type: yes/0
Extra: 01fa8641d904325f52d0652a796051f7f9226a92c06ff8d3eacd87e56986814ca20211000000064ac5aa02000000000000000000

1 output(s) for total of 495.661835575000 dcy

stealth address amount amount idx
00: e094ab4ee337ad93d21eaf20d8060096e483f011f036ca634d5598aac0f9c292 495.661835575000 46506 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": 28022, "vin": [ { "gen": { "height": 28012 } } ], "vout": [ { "amount": 495661835575, "target": { "key": "e094ab4ee337ad93d21eaf20d8060096e483f011f036ca634d5598aac0f9c292" } } ], "extra": [ 1, 250, 134, 65, 217, 4, 50, 95, 82, 208, 101, 42, 121, 96, 81, 247, 249, 34, 106, 146, 192, 111, 248, 211, 234, 205, 135, 229, 105, 134, 129, 76, 162, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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