Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41d7bc0aa9aac35bc0dab546585aae3cb155bf451cb52e5ec69d3ea867639cd5

Tx prefix hash: 652e59e2eb2660c88a5a8cfc9d1950aa8181a79025a002d180b97772eb95c036
Tx public key: dafa1decb97cdde4df682215edfec79791707a94da511f0d791643bc0131ef7b
Timestamp: 1583632625 Timestamp [UCT]: 2020-03-08 01:57:05 Age [y:d:h:m:s]: 04:254:13:48:50
Block: 78294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076751 RingCT/type: yes/0
Extra: 01dafa1decb97cdde4df682215edfec79791707a94da511f0d791643bc0131ef7b0211000000028e602c4c000000000000000000

1 output(s) for total of 337.738265802000 dcy

stealth address amount amount idx
00: dbcc6aebab28fc4d29f7c8e9988966695c8c69c17d1e0b281905a0f84ae4e8f4 337.738265802000 143738 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": 78304, "vin": [ { "gen": { "height": 78294 } } ], "vout": [ { "amount": 337738265802, "target": { "key": "dbcc6aebab28fc4d29f7c8e9988966695c8c69c17d1e0b281905a0f84ae4e8f4" } } ], "extra": [ 1, 218, 250, 29, 236, 185, 124, 221, 228, 223, 104, 34, 21, 237, 254, 199, 151, 145, 112, 122, 148, 218, 81, 31, 13, 121, 22, 67, 188, 1, 49, 239, 123, 2, 17, 0, 0, 0, 2, 142, 96, 44, 76, 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