Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d5b0200a91ce162e917602b67349690f767af24bc9764db6a4a26025ee88d52

Tx prefix hash: 2f12f23dc92c745665adf1361a4b5c7b6df784430dcffbdb2d353521bc2ad08c
Tx public key: b3226ee62f1f34e99e10f6a4489006d5837aa5863df0ab4e97ac24346ccdb088
Timestamp: 1635274568 Timestamp [UCT]: 2021-10-26 18:56:08 Age [y:d:h:m:s]: 03:138:05:12:27
Block: 361034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 876999 RingCT/type: yes/0
Extra: 01b3226ee62f1f34e99e10f6a4489006d5837aa5863df0ab4e97ac24346ccdb08802110000001a42b3953e000000000000000000

1 output(s) for total of 39.061818116000 dcy

stealth address amount amount idx
00: dd4fbe3ee7d4a4b32dce05fb8d3548fadffb9d5099ccf400dc63ddca38a5a9e4 39.061818116000 734661 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": 361044, "vin": [ { "gen": { "height": 361034 } } ], "vout": [ { "amount": 39061818116, "target": { "key": "dd4fbe3ee7d4a4b32dce05fb8d3548fadffb9d5099ccf400dc63ddca38a5a9e4" } } ], "extra": [ 1, 179, 34, 110, 230, 47, 31, 52, 233, 158, 16, 246, 164, 72, 144, 6, 213, 131, 122, 165, 134, 61, 240, 171, 78, 151, 172, 36, 52, 108, 205, 176, 136, 2, 17, 0, 0, 0, 26, 66, 179, 149, 62, 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