Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b74b4feddd12e6627bae55a34f71327a57128ecda0f989a09455bb00353792f9

Tx prefix hash: 4e012228774c4b0a58f83ef04ad72acdf38eb81c4e68ca155cfed8bdfc3692ca
Tx public key: e19ea43e18a861933cf69dc9a697304251ac19d8da328a73343efbf8e5ef98d9
Timestamp: 1700738510 Timestamp [UCT]: 2023-11-23 11:21:50 Age [y:d:h:m:s]: 01:349:03:15:16
Block: 897865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508395 RingCT/type: yes/0
Extra: 01e19ea43e18a861933cf69dc9a697304251ac19d8da328a73343efbf8e5ef98d902110000000775e3f0e9000000000000000000

1 output(s) for total of 0.650130469000 dcy

stealth address amount amount idx
00: 94e137f0ee2e956d5aceda83779f676af4bcf20a7dc4d7727d8a5edb53e5d59f 0.650130469000 1354262 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": 897875, "vin": [ { "gen": { "height": 897865 } } ], "vout": [ { "amount": 650130469, "target": { "key": "94e137f0ee2e956d5aceda83779f676af4bcf20a7dc4d7727d8a5edb53e5d59f" } } ], "extra": [ 1, 225, 158, 164, 62, 24, 168, 97, 147, 60, 246, 157, 201, 166, 151, 48, 66, 81, 172, 25, 216, 218, 50, 138, 115, 52, 62, 251, 248, 229, 239, 152, 217, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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