Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec448e392eac82c7d41b3d474198b29a2c6399c333b812bd23358cce67cc150e

Tx prefix hash: 66e15be3f58bbd00f9ec856e28bd46ae88e16661f73d255df826996dfd9a9b6b
Tx public key: 2e50736cd4057ff8a8a07961faeea16abcd233d1c6ae2770f10e03e575944cac
Timestamp: 1577835678 Timestamp [UCT]: 2019-12-31 23:41:18 Age [y:d:h:m:s]: 05:040:06:27:19
Block: 36054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178541 RingCT/type: yes/0
Extra: 012e50736cd4057ff8a8a07961faeea16abcd233d1c6ae2770f10e03e575944cac0211000000114943cd9f000000000000000000

1 output(s) for total of 466.201551621000 dcy

stealth address amount amount idx
00: 28094293b219cce5e71fd7d68b2523f92b27203d234681f7316c0f84d1dbbddc 466.201551621000 60932 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": 36064, "vin": [ { "gen": { "height": 36054 } } ], "vout": [ { "amount": 466201551621, "target": { "key": "28094293b219cce5e71fd7d68b2523f92b27203d234681f7316c0f84d1dbbddc" } } ], "extra": [ 1, 46, 80, 115, 108, 212, 5, 127, 248, 168, 160, 121, 97, 250, 238, 161, 106, 188, 210, 51, 209, 198, 174, 39, 112, 241, 14, 3, 229, 117, 148, 76, 172, 2, 17, 0, 0, 0, 17, 73, 67, 205, 159, 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