Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 497e8493d3539e41984baac4230055e16507731ff850f5975cc7499f0eea2102

Tx prefix hash: f17e1794a4a61dce148f8506fa781cf9d39415e15fa73af0f8fe5630be56254c
Tx public key: c2ca46aeaa2e5c72db55a878a39e17c061abba9ecd80a4236ea6fe99a594c76e
Timestamp: 1581210726 Timestamp [UCT]: 2020-02-09 01:12:06 Age [y:d:h:m:s]: 04:291:19:17:16
Block: 60966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100670 RingCT/type: yes/0
Extra: 01c2ca46aeaa2e5c72db55a878a39e17c061abba9ecd80a4236ea6fe99a594c76e02110000000c4ac5aa02000000000000000000

1 output(s) for total of 385.502473489000 dcy

stealth address amount amount idx
00: b56abdaa327bf88251f0e0e619dd45cb7321ad339045dfff60699af51c1d1e14 385.502473489000 112381 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": 60976, "vin": [ { "gen": { "height": 60966 } } ], "vout": [ { "amount": 385502473489, "target": { "key": "b56abdaa327bf88251f0e0e619dd45cb7321ad339045dfff60699af51c1d1e14" } } ], "extra": [ 1, 194, 202, 70, 174, 170, 46, 92, 114, 219, 85, 168, 120, 163, 158, 23, 192, 97, 171, 186, 158, 205, 128, 164, 35, 110, 166, 254, 153, 165, 148, 199, 110, 2, 17, 0, 0, 0, 12, 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