Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7342d05cc3e2648f7d610990a94eef3e2da8cb32225d749b22082c79d3de9779

Tx prefix hash: 6892761fce8b32af5d5dd6a5ae3c7d8a2a576e990173e3f324f5ba8163540ed0
Tx public key: 7421247892be09107c6924502be9bacfef7d2ae2f6e31d61cd380bd279c23422
Timestamp: 1574754035 Timestamp [UCT]: 2019-11-26 07:40:35 Age [y:d:h:m:s]: 05:034:11:17:04
Block: 17736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167462 RingCT/type: yes/0
Extra: 017421247892be09107c6924502be9bacfef7d2ae2f6e31d61cd380bd279c2342202110000001b5d286194000000000000000000

1 output(s) for total of 536.085609814000 dcy

stealth address amount amount idx
00: 6ef9f9a7c0fe1456c03b436a7025ff309ecb7238540591b011b4e4e974f1dacc 536.085609814000 26228 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": 17746, "vin": [ { "gen": { "height": 17736 } } ], "vout": [ { "amount": 536085609814, "target": { "key": "6ef9f9a7c0fe1456c03b436a7025ff309ecb7238540591b011b4e4e974f1dacc" } } ], "extra": [ 1, 116, 33, 36, 120, 146, 190, 9, 16, 124, 105, 36, 80, 43, 233, 186, 207, 239, 125, 42, 226, 246, 227, 29, 97, 205, 56, 11, 210, 121, 194, 52, 34, 2, 17, 0, 0, 0, 27, 93, 40, 97, 148, 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