Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e75e2fc8338af777f68fb1b7aae1c159a46b86fd7f6dd974400bfe51c81c03

Tx prefix hash: d0094c5ff40f57a010ab1f61c380b0b2f262938a70b34f26a3dbba90e5aaac68
Tx public key: 16a16b35de12e3db7863daeb330d1e82be834152b0c1df6acb61b1676cbfd73d
Timestamp: 1717885634 Timestamp [UCT]: 2024-06-08 22:27:14 Age [y:d:h:m:s]: 00:293:05:51:45
Block: 1040030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209552 RingCT/type: yes/0
Extra: 0116a16b35de12e3db7863daeb330d1e82be834152b0c1df6acb61b1676cbfd73d021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 616e4cd1329064a71805851557a5744cf643df0f062da9edfd366f18aaa8ccfa 0.600000000000 1508685 of 15

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": 1040040, "vin": [ { "gen": { "height": 1040030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "616e4cd1329064a71805851557a5744cf643df0f062da9edfd366f18aaa8ccfa" } } ], "extra": [ 1, 22, 161, 107, 53, 222, 18, 227, 219, 120, 99, 218, 235, 51, 13, 30, 130, 190, 131, 65, 82, 176, 193, 223, 106, 203, 97, 177, 103, 108, 191, 215, 61, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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